@Lucki would you be so kind to git rebase this PR on the WIP_3.0.0 branch. Not sure if this is handled automatically by git since the commit hashes are different. You might have to drop the first three commits manually to remove the duplicate/conflicting commits from the PR.

Sorry for the extra effort!

All done! GitHub got this correctly and no commit dropping was required. Make sure you visit #141 first!

Is it good practice to use gschemas as IPC mechanism, though?

I honestly don't know but since you already had the observer mechanism in place it wasn't far to this.

I honestly don't know but since you already had the observer mechanism in place it wasn't far to this.

Yeah, let's try and see how this works out! The only thing I want to avoid is accepting some (potentially unsafe) user input via this backend-connection.

@Lucki Again, could you please rebase the commit? Sorry for that!
If this is too annoying to you, I could pull in your changes directly without handling the PR in the GitHub UI, but I honestly don't know if I can make the GitHub interface correctly pick up the manual changes.

I want to avoid is accepting some (potentially unsafe) user input via this backend-connection.

There are only simple true/false toggles for:

• Clearing the history
• Pausing the timer
• Requesting new wallpapers
• Opening the wallpaper folder

No user input directly.

Hm, strange that this doesn't work automatic. It worked automatic locally and GitHub doesn't even register anything different in the force push…

Guess I have to rebase every PR when the previous one is merged then.

Yeah, exactly; these boolean triggers won't be an issue at all. I just realized that I have to look at all the other schemas in general and see what exactly is stored there and how it is used because I never thought about it a lot.

Yeah, the hashes change once it is merged and it is a bit annoying that GH does not recognize this.